home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group99a.txt
/
000024_icon-group-sender _Mon Feb 1 13:05:22 1999.msg
< prev
next >
Wrap
Internet Message Format
|
2000-09-20
|
1KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.9.1a/8.9.1) id NAA10611
for icon-group-addresses; Mon, 1 Feb 1999 13:05:04 -0700 (MST)
Message-Id: <199902012005.NAA10611@baskerville.CS.Arizona.EDU>
Date: Mon, 1 Feb 1999 08:48:25 -0800 (PST)
From: Shamim Mohamed <spm@drones.com>
To: Alan Sandercock <acsander@mir.gis.gatech.edu>
Cc: icon-group@optima.CS.Arizona.EDU
Subject: Re: file and directory manipulation
Errors-To: icon-group-errors@optima.CS.Arizona.EDU
Status: RO
> I've been successfully using Icon on a Unix platform (DGUX) for small
> programming jobs related to Geographical Information Processessing (GIS)
> and some text processing. We are moving to a Windows NT platform. Will I
> be able to use Unicon in this environment?
Yes, the goal for the project is to be able to use the Unicon extensions
both on Unix and on Windows. One of Clint's students has already ported most
of the features to Windows. Some of the features Unix programmers expect are
absent in NT, so those are deprecated. One example is fork/dup/exec that is
a common idiom for spawning programs on Unix; it has been subsumed by
extending system(). Please read http://www.drones.com/unicon/ for more
details. (fork, exec and dup are still available in Unix versions but are
deprecated.)
-s